Skip to main content
TrustRadius
Amazon EC2 Auto Scaling

Amazon EC2 Auto Scaling

Overview

What is Amazon EC2 Auto Scaling?

Amazon EC2 Auto Scaling helps users maintain application availability and allows users to automatically add or remove EC2 instances according to definable conditions.

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Amazon EC2 Auto Scaling?

Amazon EC2 Auto Scaling helps users maintain application availability and allows users to automatically add or remove EC2 instances according to definable conditions.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

Alternatives Pricing

What is Mirantis Kubernetes Engine?

The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters…

What is ABP Commercial?

A web development platform for modern ASP.NET Core applications based on the open-source, strong, and mature ABP Framework. Volosoft states the service provides:enterprise-ready, feature-rich, pre-built application modules (e.g. Identity Server management, SaaS management, language management,…

Return to navigation

Product Demos

AWS EC2 AutoScaling Group - Amazon Web Services Tutorial 2021

YouTube
Return to navigation

Product Details

What is Amazon EC2 Auto Scaling?

Amazon EC2 Auto Scaling Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(47)

Attribute Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Amazon EC2 Auto Scaling is a foundational component of the web - customer facing - tier of our multi-tier LAMP stack application. This allows us to scale in response to key metrics - such as CPU utilization on the web nodes - and maintain manageable traffic loads on each of the nodes in the autoscaling group. This translates to minimizing the frequency of overloaded EC2 instances requiring intervention (in some cases automated, in other cases manual) in order to be able to serve traffic again. This in turn means that the load balancer is able to serve traffic and that we are minimizing the number of 5XX errors that are surfaced to end users. This is in use in all of our AWS hosted applications. High availability is the business problem that this solves for us, as explained above.
  • Dynamic scaling can be configured to respond to a wide variety of metrics and alerts
  • Predictive scaling allows one to get ahead of high traffic events rather than simply reacting to them
  • Health checks are configurable based on the needs of your application and architecture
  • It can be confusing if you have multiple scaling policies in effect for an autoscaling group and they conflict. In that case, conflict resolution is handled by whichever policy has the greater impact. It would be more ideal if there was intelligence preventing these kinds of conflicting policies
  • It can be confusing if you have conflicting and concurrent scale out and scale in policies in effect. In this case, the scale out action will take place, in order to ensure availability. It would be more ideal if there was intelligence preventing these kinds of conflicting policies
  • IAM is always a bit confusing and the appropriate service roles are required to configure autoscaling correctly
EC2 Auto Scaling is a foundational component of high availability architectures in AWS. It allows one to dynamically scale in response to key metrics - such as CPU utilization on the web nodes - or schedule scaling based on anticipated events - such as a flash sale for an e-commerce site. By scaling horizontally, one saves money by not having to scale up to peak traffic. By maintaining manageable traffic loads on each of the nodes in the autoscaling group, one minimizes the incidence of nodes in the autoscaling group failing, which translates to higher availability of the application served by the instances. This is not to mention the possibility of hardware failure on the AWS side, a low likelihood but totally possible event. High availability is not purely a frontend or backend concern. Anything you can do with EC2s that benefits from high availability benefits from autoscaling.
  • Dynamic scaling, which allows us to configure autoscaling events in response to a wide variety of metrics and alerts
  • Predictive scaling, which allows us to get ahead of high traffic events rather than simply reacting to them
  • Custom health checks are helpful for us tuning the scaling policies in response to our application specific needs
  • Hugely positive impact on our ROI because it increases availability of our offering
  • No negative impact that can be measured. This is a totally worthwhile investment
There are no reasonable alternatives to consider when you're building a highly available application of EC2 instances in AWS. There are alternative high availability architectures to consider, including but not limited Elastic Kubernetes Service or serverless architectures. In our case, we were locked in to EC2s at the time of architecture so there was no alternative for our use case. Serverless is often a great choice but it's worth utilizing AWS tooling such as Cost Explorer to spec out potential costs of a serverless architecture as opposed to one that takes advantage of EC2 instances.
Amazon Elastic Compute Cloud (EC2), AWS CloudFormation, Amazon CloudWatch
Brandon R Hudson | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Sometimes, you start by configuring a server with the smallest configuration, but I think it is good to be able to find the one that suits your needs in the AWS market and simplify the server configuration procedure. There are so many virtual appliances that you can't choose. Because the infrastructure is handled by AWS, services may be put on the network without the need for networking skills. The greatest advantage is that users may concentrate just on programs.
  • Recovery time is surprisingly fast.
  • It is always used as a preference in conversations with other engineers.
  • Compared to other IaaS, the scale is different.
  • For newcomers, it might be a little confusing.
  • The setup procedure's content still needs a knowledge of AWS.
  • Self-learning can be beneficial, however, I found it really beneficial to share my expertise and common processes with my colleagues.
If you need to establish a system right away, in the past it took weeks or months to request a quote from the vendor and receive the equipment. Now, with Amazon EC2 in less than tens of minutes or hours, you can create a test environment and test it without any inconvenience.
  • Many on-premises server setups were successfully migrated to AWS.
  • They reacted strongly to the sensation of direction to travel to the cloud in the absence of equipment.
  • Cloud computing on an in-house system.
  • There is no need to maintain infrastructural equipment.
  • There is no need to switch the electricity off or on in the case of a legitimate power outage.
  • The system frequently had issues when turned on, and labor frequently continued on all night, but by transferring to the cloud, that effort might be spared.
The operating system, CPU, RAM, and storage may be constructed in any configuration and readily altered after the build. The most important factor is the "sense of security."Problems may arise once every several years, but there is a significant difference when discussing how to cope with hardware problems in the local age.
Trend Micro Cloud App Security, Zoom, Acronis Advanced Backup (formerly Cyber Backup Cloud)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Amazon EC2 is used to host all the servers we run our applications on.
  • Very cost effective.
  • Easy to set up and use.
  • Auto-scaling feature.
  • It can be rigid with the time periods for reserved instances.
  • Having multiple instances at the same time can be really expensive.
  • Sometimes there are issues that prevent you from accessing an instance.
It is well suited for hosting files, websites, and applications on the internet rather than using multiple third parties.
  • Sometimes customer support can be slow.
  • If you are not experienced, using the CLI can be confusing.
  • It can definitely be more flexible with prices even though it offers a good range of services.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Amazon EC2 Auto Scaling is being used by [our] development team. Due to its high technical nature dev-ops team manage the configuration. We use it for 2 main purposes: a) increase/decrease the resources based on demand b) deployment with zero down time by deploying a new server with new setup and code and removing [the[ old server after[wards].
  • Automation.
  • Increase/decrease capacity on demand based on rules.
  • Very flexible, but technical tool.
  • See server logs seamless[ly] while increasing/decreasing capacity.
  • Be much easier to manage and configure [for] a non-technical person
  • Might need other tools to make admins tasks easier.
Well suited when you really meet their requirement to handle increase/decrease resources based on demand. Without it, the process should be done manually and can be error-prone due to human intervention on repetitive tasks. Automation is the key word here. The problem would be the complexity or technicality it might add but with clear dev-ops team or documentation or a manual of how to use it might be fine.
  • Automation. Less time of human intervention for repetitive tasks.
  • Cost reduction. Pay as you [go] fits good.
  • Works fine with other AWS services.
1 year ago, without auto scaling, every time we think we might have a peak in demand, we launch a new server manually. So far we did not buy it but sometimes the server was not used at all or we forgot to remove from load balancer. Cost was affected a little bit but human intervention was always required constantly.
Usability is good since we already know how AWS works. For those that are new it might be a little bit confusing at the beginning but they are improving it at a fast pace. Even though AWS keeps changing the user interface constantly, it is still powerful, understandable and easy to use. For technical people, they still offer the CLI.
For basic and non-complex set ups there [are] a lot of tutorials and information out there on the internet. You can solve pretty much any problem you are dealing with. AWS also provides different support plans. In our case, since we have a dev-ops team we do not need any support plan yet, but we can reconsider it in the future since we are growing.
Amazon Elastic Compute Cloud (EC2), Amazon S3 (Simple Storage Service), Amazon Elastic Load Balancing
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Since it's a[n] extremely technical tool, it's being used by the engineering department. Our area uses it mainly for websites, in combination with Amazon Elastic Load Balancers (ELB), that make the perfect match.

Amazon EC2 Auto Scaling help[s] us on moments when our websites received pikes of high traffic, to keep the [server] running, and without our intervention.
  • Automatic capacity increases based on rules.
  • No user intervention.
  • Very flexible tool.
  • Sometimes decrease rules may not work.
  • New scaling policy creation is a bit confusing and do[es] no[t] have help.
  • Previous scaling policy screen no longer exists, so you need to understand what new interface actually does.
Despite the problems with the lack of information (and help) on the new user interface, Amazon EC2 Auto Scaling is a terrific tool that show[s] us easily the power of "the cloud". Only a few years ago, increasing server capacity involved weeks or months of planning, and a hefty budget in some cases. Now, with the Auto Scaling capacity, you can increase and decrease capacity with a rule, and without a long commitment and investment on hardware.
  • Simplifies server operations.
  • Reduces costs.
  • Increases application reliability.
We tried with dedicated hardware load balancers with two servers a few years ago. It was a huge investment, and involves a lot of work, mainly on the server side. Also, that was not elastic. So if we wanted to go from 2 to 3 servers, we need to buy another server. That works, but that was not a good experience.
The new interface is an improvement on several ways over the old one, but, as usual from Amazon, they changed some behaviors - so if you are already a user, probably you need to learn how to do some tasks that you used to in the new way. No explanation on why [they] changed the interface and how it's better, etc. You just you need to learn how to do it on the new interface.

Despite that annoying habit from Amazon of changing everything, the new interface is clear and works. But beware that in the future that would change again, with no explanation whatsoever.
The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems.

Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.
Return to navigation